• Test Strategy provides an overarching approach to testing. It’s a High-level document. It covers the entire project.
• Test Plan provides the specific approach and execution of tests. It’s a detailed document. It covers only to a specific project phase.

Test Scenario: High-level description of what to test.
Test Case: Detailed step-by-step execution guide.

Verification: Building the product right (development phase).
Validation: Building the right product (testing phase).

Test Case template includes Test case ID, Test Case Name, Test Data, Test Case Priority, Test Step Description, Expected Result, Actual Result, Pass/Fail Status, Tested by and Test Date.

Requirements Traceability Matrix (RTM) is used to trace the requirements are done by the testing side by matching the requirement with test cases. It has requirement ID, requirement description, test case ID, and the test case result.

Functional Testing is testing the functionality of the application. Here we test specific features and functions.
Non-Functional Testing is testing the non-functional aspects like how well it performs. Here we test performance, usability, security of the application.

QA (Quality Assurance) focuses on improving and ensuring processes that are followed to prevent defects. It ensures that the software development and testing processes are followed correctly.
QC (Quality Control) focuses on identifying and fixing defects in the product after development. It ensures the product meets the quality standards by detecting defects.

Error: It is a mistake made by a developer during coding.
Defect: It’s the variation between the actual results and expected results. If a developer finds an issue and corrects it by himself in the development phase then it’s called a defect.
Bug: If testers find any mismatch in the application in testing phase, then they call it as Bug.

Bug leakage: Bug which is missed by the testing team while testing and if it is found by the end user or customer in Live Environment.
Bug Release: Releasing the application to the Live Environment with the known bugs like low or deferred bugs.

Severity is how severe the defect is going to impact the functionality or performance of the application.
Priority is to make sure how soon the defect needs to be resolved based on business or project needs.

Waterfall is a step-by-step process where each phase must be completed before moving to the next. It needs one large cycle from start to finish.
Agile is an iterative process with flexible, shorter cycles (sprints) that allow continuous improvements and frequent feedback from the customer. It needs multiple cycles (sprints), each delivering a part of the product.

Positive Testing is to determine what system supposed to do. It helps to check whether the application is justifying the requirements or not.
Negative Testing is to determine what system not supposed to do. It helps to find the defects from the software.

Unit Testing: Test individual units of codes during development to ensure they work as expected. It’s done by Developers.
Integration Testing: Test how different components or systems interact with each other after unit testing. It’s done by Developers and Testers.
System Testing: Test the complete system to ensure all parts work together and meet the requirements. It’s done by Testers.
Acceptance Testing: Test the product in a real environment and ensure it meets business needs. It’s done by End-users or a selected group of customers as well as QA Team.

Ad-hoc testing is an informal testing type. This testing is primarily performed if the knowledge of testers in the application under test is very high.

A bug which needs to handle as more than high priority bug and needs to be fix it immediately.

Entry Criteria gives the prerequisite items that needs to start a phase.
Exit Criteria defines the items that must be concluded when a phase is completed.

Defect Triage is the process of evaluating, prioritizing, and assigning defects based on their severity and impact. It helps teams decide which defects need immediate attention and which can be deferred.

White Box Testing is done based on applications internal coding knowledge. It is done by developers.
Black Box Testing is done without looking at the internal coding knowledge. It is done by testers.

Outsprint:
To automate user stories for the previous sprint, is called out-sprint automation. Consider there were few User stories from previous Sprint which could be automated. We will automate it in current sprint, which is called as n-1 or outsprint automation.
Insprint:
To develop and automate user stories in the same sprint, is called in-sprint automation. Consider there were few user stories in a sprint which could be automated then, we will be writing skeleton scripts until the developer develop the application. Once the build is delivered to testing team, after that we will execute the scripts.

1. Testing shows the presence of defect not their absence.
2. Exhaustive testing is not possible.
3. Early testing saves time and money.
4. Defects cluster together.
5. Beware of pesticide paradox.
6. Testing is context dependent.
7. Absence of error is a fallacy.